release v3.1.0 #621
Merged
release v3.1.0 #621
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
abr-egn
approved these changes
Nov 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The docs build for the driver failed because we're using the impl introduced in #601 in the Atlas search helpers
documentation (but not in code). Fortunately the actual driver release is fine, but I guess this is something thatcargo publish --dry-runand our rustdoc lint can't catch.Edit - we're actually using the impl when
bson-3is enabled; I'm not sure why the release build didn't catch this.cargo updatewill pull in the new bson version now that it's out.My hope is that once this version is published, I can re-run the docs build and it'll pull in the new version without needing an explicit bump of the bson dep in the driver (and therefore another release).
I will also figure out a way to check this before a release to avoid a similar situation in the future 🙂